The actual call in the `run` command will be a bit more complex since we'll have to attach a stream callback and probably create a text queue iterator like what we did for Gradio, but this shows that it's possible and shouldn't be too complicated.

Sorry Jonathan, I didn't use any of your super useful generic functions, but we can do that later.

A big thing I wanted to point out is that in the `yield` generator, I need explicitly return a string (not a json object), otherwise this will not work, so the frontend needs to be able to parse that result somehow. We should sync on this but I feel jsons are strings anyways and as long as we follow the same output "formula" (ex: in the `list_models` we out `data` key vs other commands we directly return the AIConfig json), it should be fine.

```
curl http://localhost:8080/api/test_streaming -d '{"prompt_name":"get_activities"}' -X POST -H 'Content-Type: application/json'
```

This is pretty simple, I'm expecting
1. Create a thread to run the `config.run()` (`t.start()`: we're going to need this later so we can process the sream callback on the main thread)
2. Do some stuff (for now don't yield, doesn't need to be anything but final version this would be the stream callback yield output contents)
3. wait for the thread to finish executing (`t.join()`: by now the aiconfig output should be finalized)
4. Yield the final aiconfig